翻訳と辞書
Words near each other
・ Cryptogrammaceae
・ Cryptogrammoideae
・ Cryptogramophone Records
・ Cryptograms (album)
・ Cryptographic accelerator
・ Cryptographic engineering
・ Cryptographic hash function
・ Cryptographic High Value Product
・ Cryptographic key types
・ Cryptographic log on
・ Cryptographic Message Syntax
・ Cryptographic Modernization Program
・ Cryptographic Module Testing Laboratory
・ Cryptographic Module Validation Program
・ Cryptographic nonce
Cryptographic primitive
・ Cryptographic protocol
・ Cryptographic Quarterly
・ Cryptographic Service Provider
・ Cryptographically Generated Address
・ Cryptographically secure pseudorandom number generator
・ Cryptographie indéchiffrable
・ Cryptography
・ Cryptography law
・ Cryptography newsgroups
・ Cryptography Research
・ Cryptography standards
・ Cryptoheros
・ Cryptoheros sajica
・ Cryptoheros septemfasciatus


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Cryptographic primitive : ウィキペディア英語版
Cryptographic primitive
Cryptographic primitives are well-established, low-level cryptographic algorithms that are frequently used to build cryptographic protocols for computer security systems. These routines include, but are not limited to, one-way hash functions and encryption functions.
== Rationale ==

When creating cryptographic systems, designers use cryptographic primitives as their most basic building blocks. Because of this, cryptographic primitives are designed to do one very specific task in a highly reliable fashion.
Since cryptographic primitives are used as building blocks, they must be very reliable, i.e. perform according to their specification. For example, if an encryption routine claims to be only breakable with X number of computer operations, then if it can be broken with significantly less than X operations, that cryptographic primitive is said to fail. If a cryptographic primitive is found to fail, almost every protocol that uses it becomes vulnerable. Since creating cryptographic routines is very hard, and testing them to be reliable takes a long time, it is essentially never sensible (nor secure) to design a new cryptographic primitive to suit the needs of a new cryptographic system. The reasons include:
* The designer might not be competent in the mathematical and practical considerations involved in cryptographic primitives.
* Designing a new cryptographic primitive is ''very'' time-consuming and ''very'' error prone, even for experts in the field.
* Since algorithms in this field are not only required to be designed well, but also need to be tested well by the cryptologist community, even if a cryptographic routine looks good from a design point of view it might still contain errors. Successfully withstanding such scrutiny gives some confidence (in fact, so far, the only confidence) that the algorithm is indeed secure enough to use; security proofs for cryptographic primitives are generally not available.
Cryptographic primitives are similar in some ways to programming languages. A computer programmer rarely invents a new programming language while writing a new program; instead, they will use one of the already established programming languages to program in.
Cryptographic primitives are one of the building block of every crypto system, e.g., TLS, SSL, SSH, etc. Crypto system designers, not being in a position to definitively prove their security, must take the primitives they use as secure. Choosing the best primitive available for use in a protocol usually provides the best available security. However, compositional weaknesses are possible in any crypto system and it is the responsibility of the designer(s) to avoid them.

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Cryptographic primitive」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.